System and method for billing IP-based wireless telecommunications in a converged network

ABSTRACT

A system and method for collaborating with a billing system is provided for use in a converged telecommunication network that includes a cellular telephone network and an IP-based network. During an IP-based call registration process, a mobile device communicates with a network controller over the IP-based network. The network controller accesses a database with the information provided by the mobile device and subsequently overloads values for an existing field in a call detail record (CDR). Upon completion of the call over the IP-based network, the network controller communicates the overloaded version of the CDR to an MSC which generates the final CDR that is used for billing. Any appropriate field of the CDR can be selected for overloading, such as for example an existing CGI record field from the CDR.

RELATED APPLICATIONS

This utility patent application is a U.S. National Stage application ofInternational Application No. PCT/US06/39688, entitled “SYSTEM ANDMETHOD FOR BILLING IP-BASED WIRELESS TELECOMMUNICATIONS IN A CONVERGEDNETWORK,” filed Oct. 11, 2006, which claims the benefit under 35 UnitedStates Code §119(e) of U.S. Provisional Patent Application No.60/726,105, which was filed Oct. 12, 2005.

FIELD OF THE INVENTION

The present invention relates to billing systems in convergedtelecommunication networks. More specifically, the present invention isrelated to billing systems and methods of embedding billing relatedinformation in call detail record fields.

BACKGROUND

A variety of technologies enable telecommunication services to beoffered using Internet Protocol (IP). Commonly referred to as Voice overIP, or VoIP, such technologies enable telecommunications on any publicor private IP network, including the Internet. VoIP technology permits auser to receive IP-based telecommunications services through a varietyof devices, including a desktop computer, a notebook computer, an analoghandset used in conjunction with a VoIP telephone adapter, aVoIP-enabled handset, or other like device.

Increasingly, mobile devices, such as notebook computers, personaldigital assistants (PDAs), wireless handhelds, wireless handsets, orother similar devices, are also being enabled to receive IP-basedtelecommunications services. Such services are provided by enabling themobile device to communicate with a wireless router and access anyIP-based wireless access network, such as a network based on the IEEE802.16 (WiMAX), IEEE 802.20 Mobile Broadband Wireless Access (MBWA),Ultra Wideband (UWB), 802.11 wireless fidelity (Wi-Fi), and Bluetoothstandards.

Moreover, dual-mode mobile telecommunications devices may be enabled tocommunicate with any IP-based wireless access network. For instance,Unlicensed Mobile Access (UMA) technology allows wireless serviceproviders to merge cellular networks, such as Global System for MobileCommunications (GSM) networks, and IP-based wireless networks into oneseamless service with one mobile device, one user interface, and acommon set of network services for both voice and data. UMA technologyhas recently been accepted into release 6 of the 3rd GenerationPartnership Project (3GPP) standard as a General Access Network (GAN).With UMA or GAN solutions, subscribers may move between cellularnetworks and IP-based wireless networks with seamless voice and datasession continuity as transparently as they move between cells withinthe cellular network. Seamless in-call handover between the IP-basedwireless network and cellular network ensures that the user's locationand mobility do not affect the services delivered to the user. Servicesmay be identical whether connected over the IP-based wireless network orthe cellular network. UMA technology effectively creates a parallelradio access network, the UMA network, which interfaces to the mobilecore network using standard mobility-enabled interfaces. The mobile corenetwork remains unchanged. The common mobile core network makes itpossible for the service provider to have full service and operationaltransparency. The existing service provider Business Support Systems(BSS), service delivery systems, content services, regulatory compliancesystems, and Operation Support Systems (OSS) can support the UMA networkwithout change. Service enhancements and technology evolution of themobile core network apply transparently to both cellular access and UMA.

The present disclosure has identified a number of problems in billingsystems for converged networks such as UMA. Although the convergence ofcellular and IP-based wireless telecommunications technologies offersubstantial benefits to users, cellular service providers face manyobstacles in implementing the IP-based component of converged productand service offerings. Service providers must implement new methods andsystems, or adapt methods and systems currently implemented for thecellular component of their networks, of rating and billing of users'wireless communications. Cellular service providers' billing systems arearranged to interpret and scale for cellular-based call detail records.As such, cellular service providers are ill equipped to handle billingbased on access points and broadband Internet networks.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments are described with referenceto the following drawings.

FIG. 1A illustrates example converged wireless networks combining acellular network with an IP-based access network (in this case, a UMAnetwork).

FIG. 1B illustrates another example system that combines a cellulartelephone network with an IP-based network (in this case, a UMAnetwork).

FIG. 2 is a conceptual diagram illustrating an IP-based network system(in this example a UMA network) and billing operations using Call DetailRecords (CDR) for billing operations according to one embodiment.

FIG. 3 illustrates a system for overloading of CGI_(BILLING) recordbased on CGI_(REAL) record and database records to include in CallDetail Records for billing operations.

FIG. 4 is a diagram illustrating actions in an IP-based network (in thisexample a UMA network) for registering handset and facilitating a callfrom the handset.

FIG. 5 illustrates a logic flow diagram for a process of registering ahandset in an IP-based network, (in this example a UMA network).

FIG. 6 illustrates a logic flow diagram for a process of facilitatingand billing a call from a handset in an IP-based network (in thisexample a UMA network).

DETAILED DESCRIPTION

The present disclosure now will be described more fully hereinafter withreference to the accompanying drawings, which form a part hereof, andwhich show, by way of illustration, specific exemplary embodiments forpracticing the invention. This disclosure may, however, be embodied inmany different forms and should not be construed as limited to theembodiments set forth herein; rather, these embodiments are provided sothat this disclosure will be thorough and complete, and will fullyconvey the scope to those skilled in the art. Among other things, thepresent disclosure may be embodied as methods or devices. Accordingly,the present disclosure may take the form of an entirely hardwareembodiment, an entirely software embodiment or an embodiment combiningsoftware and hardware aspects. The following detailed description is,therefore, not to be taken in a limiting sense.

Briefly stated, the present disclosure relates to a system and methodfor collaborating with a billing system for use in a convergedtelecommunication network that includes a cellular telephone network andan IP-based network. During an IP-based call registration process, amobile device communicates with a network controller over the IP-basednetwork. The network controller accesses a database with the informationprovided by the mobile device and subsequently overloads values for anexisting field in a call detail record (CDR). Upon completion of thecall over the IP-based network, the network controller communicates theoverloaded version of the CDR to an MSC which generates the final CDRthat is used for billing. Any appropriate field of the CDR can beselected for overloading, such as for example an existing CGI recordfield from the CDR.

Converged Cellular and IP-Based Wireless Telecommunications Networks

In a converged wireless network, a cellular carrier, such as a GSM orCDMA carrier, may additionally offer wireless telecommunicationsservices over an alternate IP-based wireless telecommunications network,such as the Internet. For instance, Unlicensed Mobile Access (UMA)technology allows cellular service providers to offer their products andservices seamlessly over Internet-connected broadband networks.Dual-mode mobile devices may utilize licensed spectrums (such asspectrums for cellular communications) and alternate licensed andunlicensed spectrums (such as spectrums that may be used for IP-basedcommunication). For example, dual-mode cellular phones may access acellular network, such as a GSM network, or an IP-based wirelessnetwork, such as a network based on the IEEE 802.16 (WiMAX), IEEE 802.20Mobile Broadband Wireless Access (MBWA), Ultra Wideband (UWB), 802.11wireless fidelity (Wi-Fi), or Bluetooth standards. The IP-based networksmay also be accessed via wireless access points that are typicallyconnected to a DSL (Digital Subscriber Line) modem, a cable modem, asatellite modem, or any other broadband Internet connection. Accesspoints may be public or private, and may be located in a subscriber'shome, in public locations such as coffee shops, libraries, or schools,or in corporate locations.

When a dual mode mobile device accesses an IP-based wireless network,information is formatted in its native protocol, such as CDMA or GSMsystem protocols, and then encapsulated into Internet Protocol (IP)packets, transmitted to the access point, and communicated over theInternet to the cellular service provider's mobile core network. Suchtransmission bypasses the service provider's existing network of radiotowers. Because the same native protocols are used in communicationsinvolving IP access points as with traditional radio towers, thecellular service provider maintains a large degree of systemcompatibility even though using an IP-based network. The systems of thecellular service provider that deliver content and handle mobility maynot even need to be aware that a subscriber's mobile device is on analternate wireless network. The system may instead assume the mobiledevice is on its native cellular network. The IP network is thereforeabstracted with respect to the cellular network, regardless of whetherthe mobile device connects to the cellular network via a base station(for licensed spectrum access) or a wireless access point (for licensed,semilicensed or unlicensed spectrum access).

A non-exhaustive list of products and services available on IP-basedwireless networks includes not only voice services, but alsosupplementary services like call forwarding and call waiting, textmessaging services like SMS, and data-based services like ringtonedownloads, game downloads, picture messaging, email and web browsing.Further, since a dual-mode mobile device is connected to an IP network,all manner of data services available over such networks may be providedto the mobile device.

FIG. 1A is an illustration of a system 100 that combines a cellulartelephone network with an IP-based wireless network, in this case a UMAnetwork. The described system 100 accepts registration requests and callconnections from a mobile subscriber (MS) or mobile device 110 to eithera cellular telephone network or to an IP-based wireless network.

The example cellular telephone network includes one or more basetransceiver stations (BTS) 120 that are configured to accept cellularcommunications 112 from mobile device 110. The base transceiver stationsare connected to a base station controller/radio network controller(BSC/RNC) 176 via a private network 130. The private network 130 caninclude a variety of connections such as T1 lines, a wide area network(WAN), a local area network (LAN), various network switches, and othersimilar components. BSC/RNC 176 controls network communication trafficto the carrier network 190, where all communications are managed. Anexample carrier network 190 includes a mobile switching center (MSC)192, which is configured to control data/call flows, perform loadbalancing, as well as other functions. A variety of system databases arealso accessed in the carrier network such as, e.g., an operation supportsubsystem (OSS) database 194, a business support system (BSS) database196, and a home location register (HLR) database 198, for billing, calllogging, etc.

The example IP-based wireless network (in this case a UMA network)includes one or more access points (APs) 140 that can accept IPcommunications 114 from mobile device 110. An access point can beconfigured as part of a wireless network in one or more locations suchas a public network 142, a home network 144, or a private businessnetwork 146. Each access point is coupled to an Internet Protocol (IP)network 150 through a broadband connection. IP packets that carrycommunications (data, voice, SMS, etc.) are routed from the accesspoints to a security gateway (SGW) 171 through the IP network 150. Thesecurity gateway controls access to the network controller (in thiscase, a UMA Network Controller (UNC)) 166, which communicates with adatabase 168 for logging and accessing various data associated withcommunications. The network controller 166 is also configured to manageaccess with the carrier network 190 in a similar manner to thatperformed by the BSC/RNC 176.

Authentication of a request for access by a mobile device over theIP-based network is handled by the security gateway 171, whichcommunicates with an authentication and access authorization (AAA)module 172 as shown in FIG. 1A. Challenges and responses to requests foraccess by the mobile device are communicated between home locationregister (HLR) database 198 and the AAA module 172. When authorizationis granted, the security gateway 171 communicates the assignment of anIP address to the mobile device 110 that requested access. Once the IPaddress is passed to the mobile device 110 by the security gateway 171,the public IP address assigned to the device is passed to the networkcontroller 166.

FIG. 1B illustrates another example system that combines a cellulartelephone network with an IP-based network (in this case, a UMAnetwork). The described system 100′ accepts registration requests andcall connections from a mobile device 110 to either a cellular telephonenetwork (not shown) or to an IP-based wireless network. The system 100′includes one or more access points (AP) 140 that accept communications114 from mobile device 110. Each access point is coupled to an IPnetwork 150 through a broadband connection. IP network 150 routescommunications (data, voice, SMS, etc.) between the access points and asecurity gateway (SGW) 171. The security gateway 171 controls access tothe network controller 166, which communicates with a database (notshown) for logging and accessing various data associated withcommunications. Authentication, access, and authorization are handled bySGW 171 via AAA module 172, as previously described.

For the example system 100′, the signaling path of an IP-based call isrouted through the network controller 166 to a mobile switching system(MSS), while the voice bearer path is routed through the networkcontroller 166 to a media gateway (MGW). The signaling portion of acommunication governs various overhead aspects of the communication suchas, for example, when the call starts, when the call stops, initiating atelephone ring, etc. The voice bearer portion of the communicationcontains the actual content (either data or voice information) of thecommunication. The media gateway controls the content flow between theservice provider and the mobile device 110, while the mobile switchingsystem controls the signaling flow (or controls overhead-related flow)between the service provider and the mobile device 110.

FIG. 2 is a conceptual diagram illustrating an IP-based wireless networksystem 200 (in this example a UMA network) and billing operations usingCall Detail Records (CDR) for billing operations according to oneembodiment. Using existing call detail record fields prevents the needto modify MSCs (Mobile Switching Centers) thus limiting themodifications to the billing system. Examples of existing call detailrecord fields include those record fields defined for 2G and 3G cellularnetworks in applicable specifications, such as the 3GPP and 3GPP2specifications. Furthermore, billing system modifications, especiallymediations modifications, may be minimized by adding a specific flag.This may be accomplished by populating (i.e., overloading) an existingfield of the CDR such as, for example, the MCC (Mobile Country Code) subfield portion of the starting CGI (Cell Global Identifier) with aspecific value.

According to some embodiments, the presence of a UMA call detail recordmay be flagged using an existing call detail record field (e.g., MCC).Using an existing CDR (Call Detail Record) field minimizes the impact tocellular service provider systems involved in billing subscribers.

In principle, a CGI value is the concatenation of MCC (Mobile CountryCode)—MNC (Mobile Network Code)—LAC (Location Area Code)—Cell ID. Theyare used to identify individual GSM transmission cells and the carrierthat operates them. These CGI values are reported to a UNC (UMA NetworkController) when a UMA terminal registers to the network. The cellularservice provider may use these reported CGI values to determine whetheror not UMA should be offered. For example, there maybe some countrieswhere the cellular service provider may not offer “home” based service.In this case, the cellular service provider could choose not to provideservice or to redirect the terminal to another UMA or GSM provider. Thecellular service provider may further use the reported CGI values toassist in determining the optimum serving UNC for a mobile terminal.

Network 200 has the same basic organization as FIG. 1A and is labeledidentically where appropriate. The described system 200 acceptsregistration requests and call connections from a mobile subscriber (MS)or mobile device 110 to either a cellular telephone network or to anIP-based wireless network.

Mobile device 110 can communicate with a nearby base transceiver station(BTS) 122 when a cellular based communication is initiated. During thecall setup for the cellular based communication, a call detail record(272) is initialized with various CGI values. Example CGI valuesincluding MCC, MNC, LAC and CELLID are illustrated by CGI_(REAL) 272.

Mobile device 110 also communicates with the IP-based wireless network(in this case a UMA network) 150 through a wireless access point 142.The wireless access point 142 is configured to accept IP communications114 from mobile device 110 subject to various authenticationrequirements. IP packets that carry communications (data, voice, SMS,etc.) are routed from the access points to a security gateway (SGW) thatcontrols access to the IP-based network controller (in this case, a UMANetwork Controller (UNC) 166), which communicates with a database 168for logging and accessing various data associated with thecommunications. The IP packets are routed from the network controller166 to a mobile switching center (MSC) 192, which is configured tocontrol data/call flows, perform load balancing, as well as otherfunctions.

Upon completion of a call, MSC 192 generates a CDR (Call Detail Record)278 that is utilized by a billing system 280 for mediation 282, guiding284, rating 286 and generating bills 288. CDR 278 includes a CGI(CGI_(BILLING)) an International Mobile Subscriber Identity (IMSI) ID, astart time associated with the call, and an end time for the call.

CGI_(BILLING) is provided to MSC 192 by UNC 166. Mobile device (110)communicates its IMSI ID to UNC 166 during the initial call setup, alongwith a CGI (CGI_(REAL)), and any other information associated with thewireless network. CGI_(REAL) is a CGI that is associated with the nearbyBTS 122, which includes information such as MCC, MNC, LAC and CELL ID.The information associated with the wireless network can include theSSID and the MAC address (MAC_(AP)) associated with the wireless accesspoint 142. The UNC uses the various information 275 such as IMSI ID,SSID, MAC_(AP) to access database 168, which returns CGI_(BILLING).

FIG. 3 illustrates a system 300 for overloading of CGI_(BILLING) recordbased on CGI_(REAL) record and database records to include in CallDetail Records for billing operations. System 300 has the same basicorganization as FIG. 2 and is labeled identically where appropriate.

Network controller 166 can be arranged to manage any number ofconcurrent communications between mobile devices 110 and MSC 192. Eachmobile device 110 includes its own IMSI ID and a CGI_(BILLING) record,which can be managed in a dynamically generated session table 375. Aftera communication is concluded the overloaded CGI record (e.g.,CGI_(BILLING) 374) for the concluded communication is communicated toMSC 192, which provides the relavant call information to a billingserver 380 in the form of a CDR 278.

As previously described UNC 166 generates a CGI_(BILLING) record duringa call setup by accessing database 168 with CGI_(REAL) (in this example272). Database 168 may utilize any number of methods to identify themost appropriate CGI value, where database 168 may include fields forsubscribers 198-1, service types 198-2, zones 198-3 and access points198-X. The database fields may in some examples be other databases thatare accessed. The subscriber database may include a list of authorizedsubscribers based upon IMSI ID, or any other appropriate indicia. Theservice type database may include a list of authorized services for asubscriber, or for a region based on availability. The zones databasemay include a home service region identifier for a subscriber such as atime zone, or a calling zone region, etc. The access points database mayinclude a list of authorized access points. The various database entriesare accessed to generate the CGI_(BILLING) record.

CGI records have a number of record fields that are used to identifyvarious things related to cellular communications. In particular,cellular communications utilize fields such as MCC, MNC, LAC and CELL IDto identify the nearby BTS. Since these fields are not relevant forwireless IP-based communications, these fields can be re-used oroverloaded to populate the fields with other information that MSC 192can use to generate call detail records (CDRs). Overloaded values forthe CGI record are illustrated by CGI_(BILLING) record 374.

In a system according to some embodiments:

-   -   The system may provide a database to store GSM transmission        network CGIs and information related to those CGI values.    -   The CGI database may support partial entries such as MCC, MNC        value pairs.    -   The CGI database may support wild card ranges of CGI values or        partial CGI values.    -   The CGI database may support a Visited UNC value specifying the        visited UNC to redirect the mobile to.    -   The CGI database may support storing a list of Preferred Home        Serving UNCs for CGI entries.        Billing Events

In another system according to some embodiments:

-   -   All unbilled usage may be available for customer care viewing        just as GERAN (GSM/Edge Radio Access Network) calls. These        records may include UMA indication regardless of if the        subscriber has an add-on UMA SOC.    -   All billable events available in GERAN may be available over the        UMA system.    -   Billable events may be consistent between UMA and GERAN.    -   A call that starts on the UMA system that hands into GERAN may        be considered as if it were on the UMA transport for the entire        duration of the call. The opposite (call starts in GERAN and        hands into UMA) may also be supported as if the call were on the        GSM network for its entirety.    -   The UNC may send the billing CGI value derived at URR        registration or URR redirect, whichever is the most recent, for        inclusion in UMA CDRs.    -   If a specific CGI value is not available for the subscriber        database, a default value unique to the UMA system may be        reported.    -   Call detail records coming from the MSC may be maintained        unchanged except in CGI related CDR fields.    -   All unbilled usage may be made available for web-based viewing        just as GERAN calls. These records may include UMA indication        only if the subscriber has an add-on UMA SOC.        Rating

In some systems:

-   -   CGI values may be used to indicate UMA rating in CDRs.    -   The LAC component of the CGI may indicate time zone to the        billing system. There may be an established mapping of LAC to        U.S. time zones. This mapping may exist in engineering systems        or COS systems.    -   The billing system may support a configurable UMA DEFAULT area        definition table that allows for insertion of CGI values and        ranges (CellID+Location area) as the definition of the Wi-Fi        area. These definitions may mirror the CGIZ values in the UMA        Service Zone database.    -   The co-ordination as described above may be done so that        multiple ranges of CGIs can be distinguished in the billing        system for rating purposes.

FIG. 4 is a diagram 400 illustrating actions in an IP-based network (inthis example a UMA network) for registering handset and facilitating acall from the handset 110. The call registration process is illustratedby communication steps 401-406, while the calling process is illustratedby communication steps 407-413.

As shown in FIG. 4, a call is imitated when a handset 110 requests toregister with the security gateway (SGW) 162 over the IP access network150 at step 401. SGW 162 replies with an authentication challenge thatis communicated back to the handset 110 at step 402. At step 403, thehandset 110 responds to the authentication challenge with a responsethat is communicated to SGW 162. Also at step 403, SGW 162 communicatesa public IP address assigned to the access point for the network to thenetwork controller 166. The handset 110 also communicates the IMSI IDand a CGI record (CGI_(REAL)) to the SGW 162. At step 404, the SGW 162transmits the IMSI ID, CGI_(REAL) along with the SSID and MAC address(MAC_(AP)) from the access point in a communication to the networkcontroller 166. Network controller (UNC) 166 communicates with database168 at step 404, which replies with CGI_(BILLING) at step 405. At step406, network controller 166 communicates a registration completion tothe handset 110.

Once the registration is completed, handset 110 can communicate withnetwork controller 166 to request a call as illustrated by step 407. Atstep 408, the network controller 166 communicates the IMSI ID andCGI_(BILLING) to MSC 192. MSC 192 authorizes the call at step 409 suchthat the handset 110 can communicate over a communication channel thatis established through MSC 192 at step 411. At step 413, the call isterminated and MSC 192 communicates a CDR that includes the overloadedCGI_(BILLING) information to the billing system 280.

FIG. 5 illustrates a logic flow diagram 500 for a process of registeringa handset 110 in an IP-based wireless telecommunications network (inthis example a UMA network). The registration process, which is similarto that described above for FIG. 4, is illustrated by process steps502-528.

At step 502 the registration request is received. A challenge istransmitted to the handset 110 at step 504. At step 506 the systemreceives a response to the challenge from the handset 110. At step 508,the response from the handset is evaluated. Processing continues fromstep 508 to step 510 when the response in unacceptable, where therequest is rejected at step 510. Otherwise, processing continues fromstep 508 to step 512.

At step 512, a network controller (e.g., a UNC in a UMA network) isassigned to handle the connection. Proceeding to step 514, the public IPaddress associated with the access point that the handset 110 used toaccess the network is communicated to the network controller. At step516 the SSID and MAC address (MAC_(AP)) from the access point arecommunicated to the network controller, along with the IMSI ID andCGI_(REAL) from the handset 110. At step 518 the various informationreceived at the network controller is evaluated to determine if accessto the network is granted (e.g., the UMA network). Processing flows fromstep 518 to step 520 when access is denied, where the request isrejected at step 520. Otherwise, processing continues from step 518 tostep 522.

At step 522, MAC_(AP) and CGI_(REAL) are transmitted to the database(e.g., a UMA database) such as in the form of a database query. Thedatabase generates CGI_(BILLING) in response to the query at step 524.Proceeding to step 524, the database transmits CGI_(BILLING) to thenetwork controller (e.g., UNC). At step 528, the registrationauthorization is transmitted to the handset.

FIG. 6 illustrates a logic flow diagram 600 for a process offacilitating and billing a call from a handset 110 in an IP-basednetwork (in this example a UMA network). The calling process, which issimilar to that described above for FIG. 4, is illustrated by processsteps 602-616.

At step 602 the call request is received by the network controller(e.g., UNC 166). Proceeding to step 604, CGI_(BILLING) is transmittedfrom the network controller to the MSC (e.g., MSC 192). Processingcontinues from step 604 to step 606 where the information is evaluatedto determine if the call is permitted. Processing flows from step 606 tostep 608 when the call is rejected, where a call reject is generated atstep 608. Otherwise, processing continues from step 606 to step 610.

At step 610, the call is authorized. Flowing to step 612, the call isfacilitated such as by transferring IP packets for the call through thewireless IP network to the MSC. At step 614, the call is continuallymonitored to determine if the call has been completed (terminated) suchas by a call hang-up or via an inadvertently dropped call. Processingcontinues to step 612 when the call is ongoing, or to step 616 when thecall has been completed. At step 616 the CDR is transmitted to thebilling system, where the CDR includes the information from theoverloaded CGI record (CGI_(BILLING)).

The present disclosure is not limited to the above-describedenvironment. Many other configurations of computing devices,communications, applications, and distribution systems may be employedto implement a system for identifying UMA call detail records usingexisting call detail record fields.

According to some embodiments, a computer-implemented method forfacilitating Call Detail Record (CDR) billing in a converged wirelesssystem and an Internet telephony system may begin with receiving aregistration request over the Internet telephony system from a handsetthat is capable of using the wireless system and the Internet telephonysystem and is identified by a wireless identifier. An Internet telephonycell identity is selected with a gateway node referenced by the wirelessidentifier after the registration request is received.

The method further includes modifying at least one existing radio cellidentity field with the Internet telephony cell identity such that themodified radio cell identity field corresponds to an Internet telephonycall and identifying a call request from the handset over the Internettelephony system. The modified radio cell identity field is thencommunicated to a switch for the identified call request. Successfulregistration may also be communicated to the handset.

The Internet telephony cell identity is selected by providing a radiocell identity from the handset to an Internet telephony system database,and receiving the Internet telephony cell identity from the Internettelephony system database.

The method also includes facilitating the Internet telephony system callfor the handset in response to the Internet telephony system callrequest, and communicating a CDR that includes the Internet telephonycell identity from the switch to a billing system upon completion of theInternet telephony system call.

The Internet telephony call identity may include at least one of: amodified Mobile Country Code (MCC) field, a modified Mobile Network Code(MNC) field, a modified Location Area Code (LAC) field, and a modifiedCell ID field. The MCC field may be populated with a value indicatingthe Internet telephony system call request is made over the Internettelephony system.

Furthermore, the LAC and Cell ID fields may be populated with a valuepair that identifies the Internet telephony system call request as beingfor one of: an in-country call, an out-of-country call, a call made neara tower belonging to the wireless system, and a call made near a towerbelonging to another wireless system.

In another embodiment, a gateway node may be assigned based on a publicIP address associated with the Internet telephony system. The Internettelephony system database may include at least one of: a subscriberdatabase, a service type database, a zones database, and an accesspoints database.

Where a security node is employed, the security node may be configuredto authenticate the handset by a security gateway prior to registration,communicate a public IP address associated with the access network tothe gateway node as part of the authentication, and assign the gatewaynode based on the public IP address.

The switch may be arranged to communicate a start time and an end timeassociated with the Internet telephony system call to the billing systemupon completion of the Internet telephony system call.

Many of the examples described above reference the CGI record as theselected field that is used for overloading in the CDR. The CGI recordis merely one example field in the CDR, and any other appropriate fieldmay be selected for overloading without departing from the scope of thepresent disclosure.

The above specification, examples and data provide a completedescription of the manufacture and use of the composition of theembodiments. Although the subject matter has been described in languagespecific to structural features and/or methodological acts, it is to beunderstood that the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims and embodiments.

1. A computer-implemented method for facilitating Call Detail Record(CDR) billing in a converged cellular system and an IP-based wirelesssystem, the method comprising: receiving a registration request over theIP-based wireless system from a handset that is capable of using thecellular system and the IP-based wireless system and is identified by awireless identifier; selecting an IP-based wireless cell identity with agateway node referenced by the wireless identifier after theregistration request is received; overloading at least one existingfield from a cellular call detail record with the IP-based wireless cellidentity such that the overloaded cellular call detail record fieldcorresponds to an IP-based wireless call; identifying a call requestfrom the handset over the IP-based wireless system; and communicatingthe overloaded cellular call detail record to a switch for theidentified call request, wherein the overloaded cellular call detailrecord reflects, at least in part, a handover from the IP-based wirelesssystem to the cellular system or from the cellular system to theIP-based wireless system.
 2. The computer-implemented method of claim 1,further comprising communicating successful registration to the handset.3. The computer-implemented method of claim 1, wherein selecting theIP-based wireless cell identity includes: providing a radio cellidentity from the handset to an IP-based wireless system database; andreceiving the IP-based wireless cell identity from the IP-based wirelesssystem database.
 4. The computer-implemented method of claim 1, furthercomprising: facilitating the IP-based wireless system call for thehandset in response to the IP-based wireless system call request; andcommunicating the overloaded cellular call detail record that includesthe IP-based wireless cell identity from the switch to a billing systemupon completion of the IP-based wireless system call.
 5. Thecomputer-implemented method of claim 1, wherein the IP-based wirelesscell identity includes at least one of: a modified Mobile Country Code(MCC) field, a modified Mobile Network Code (MNC) field, a modifiedLocation Area Code (LAC) field, and a modified Cell ID field.
 6. Thecomputer-implemented method of claim 5, wherein the MCC field ispopulated with a value indicating the IP-based wireless system callrequest is made over the IP-based wireless system.
 7. Thecomputer-implemented method of claim 5, wherein the LAC and Cell IDfields are populated with a value pair that identifies the IP-basedwireless system call request as being for one of: an in-country call, anout-of-country call, a call made near a tower belonging to the cellularsystem, and a call made near a tower belonging to another cellularsystem.
 8. The computer-implemented method of claim 1, furthercomprising assigning the gateway node based on a public IP addressassociated with the IPbased wireless system.
 9. A gateway node havingcomputer-readable instructions for facilitating Call Detail Record (CDR)billing in a converged cellular system and an IP-based wireless system,the instructions comprising: receiving a registration request associatedwith a handset over an IP-based wireless system, wherein theregistration request includes identification information comprising atleast one of: a wireless identity, a radio cell identity, an SSID, and aMAC address; accessing an IP-based wireless system database with theidentification information; receiving an IP-based wireless cell identityfrom the IP-based wireless system database; overloading at least oneexisting field from a cellular call detail record with the IP-basedwireless cell identity such that the overloaded cellular call detailrecord field corresponds to an IP-based wireless system call, whereinthe overloaded cellular call detail record reflects, at least in part, abilling event; identifying a call request from the handset over theIP-based wireless system; and communicating the overloaded cellular calldetail record to a switch for the identified call request.
 10. Thegateway node of claim 9, wherein the instructions further include:receiving a public IP address associated with the IP-based wirelesssystem from a security node prior to receiving the request forregistration; and communicating successful registration to the handset.11. The gateway node of claim 9, wherein the IP-based wireless cellidentity includes at least one of: a modified Mobile Country Code (MCC)field, a modified Mobile Network Code (MNC) field, a Location Area Code(LAC) field, and a Cell ID field.
 12. The gateway node of claim 11,wherein the MCC field is populated with a value indicating the IP-basedwireless system call is made via the IP-based wireless system; and theLAC and Cell ID fields are populated with a value pair that identifiesthe IP-based wireless system call as being one of: an in-country call,an out-of-country call, a call made near a tower belonging to thecellular system, and a call made near a tower belonging to anothercellular system.
 13. A system for facilitating Call Detail Record (CDR)billing in a converged cellular system and an IP-based wireless system,the system comprising: a gateway node that is configured to: receive aregistration request from a handset using an IP-based wireless system,wherein the request includes identification information comprising atleast one of a wireless identity, a radio cell identity, an SSID, and aMAC address; access an IP-based wireless system database with theidentification information; receive an IP-based wireless cell identityfrom the IP-based wireless system database; overwrite at least oneexisting field from a cellular call detail record with the IP-basedwireless cell identity such that the overwritten cellular call detailrecord field corresponds to an IP-based wireless system call, whereinoverwritten cellular call detail record reflects, at least in part, abilling event; and identify a call request from the handset over theIP-based wireless system; and a switch that is configured to: receivethe overwritten cellular call detail record from the gateway node forthe identified call request; facilitate an IP-based wireless system callfrom the handset in response to the call request; and communicate theIP-based wireless cell identity to a billing system upon completion ofthe IP-based wireless system call.
 14. The system of claim 13, whereinthe IP-based wireless system database is configured to determine theIP-based wireless cell identity based on the received identificationinformation, wherein the IP-based wireless system database includes atleast one of: a subscriber database, a service type database, a zonesdatabase, and an access points database.
 15. The system of claim 13,further comprising a security node that is configured to: authenticatethe handset by a security gateway prior to registration; communicate apublic IP address associated with the access network to the gateway nodeas part of the authentication; and assigne the gateway node based on thepublic IP address.
 16. The system of claim 13, wherein the gateway nodeis further configured to overwrite the existing call detail recordfields such that an MCC field is overwrite with a value indicating theIP-based wireless system call is made via the access network.
 17. Thesystem of claim 13, wherein the gateway node is further configured tooverwrite the existing call detail record fields such that LAC and CellID fields are populated with a value pair that identifies the IP-basedwireless system call as being one of: an out-of-country call, a callmade near a tower belonging to the cellular system, and a call made neara tower belonging to another cellular system.
 18. The system of claim13, wherein the switch is further configured to communicate a start timeand an end time associated with the IP-based wireless system call to thebilling system upon completion of the IP-based wireless system call. 19.The system of claim 13, further comprising a radio cell identitydatabase configured to store information associated with the handsetwhen it uses a cellular system component of the converged systems.
 20. Acomputer-implemented method for facilitating Call Detail Record (CDR)billing in an Unlicensed Mobile Access (UMA) network, the methodcomprising: receiving a registration request from a UMA capable handsetthat is identified by an International Mobile Subscriber Identity (IMSI)ID, wherein the UMA capable handset is using an access network;selecting a Cell Global Identification (CGI_(BILLING)) ID with a UMANetwork Controller (UNC) referenced by the IMSI ID Mier the registrationrequest is received; overloading at least one existing CGI field withthe CGI_(BILLING) ID such that the overloaded CGI field corresponds to aUMA call; identifying a call request from the UMA capable handset overthe access network; and communicating the overloaded CGI field to aMobile Switching Center (MSC) for the identified call request.
 21. Thecomputer-implemented method of claim 20, further comprisingcommunicating successful registration to the UMA capable handset. 22.The computer-implemented method of claim 20, wherein selecting theCGI_(BILLING) ID includes: providing a CGI_(REAL) ID from the UMAcapable handset to a UMA database; and receiving the CGI_(BILLING) IDfrom the UMA database.
 23. The computer-implemented method of claim 20,further comprising: facilitating the UMA call for the UMA capablehandset in response to the UMA call request; and communicating a CDRthat includes the CGI_(BILLING) ID from the MSC to a billing system uponcompletion of the UMA call.
 24. The computer-implemented method of claim20, wherein the CGI_(BILLING) ID includes at least one of: a modifiedMobile Country Code (MCC) field, a modified Mobile Network Code (MNC)field, a Location Area Code (LAC) field, and a Cell ID field.
 25. Thecomputer-implemented method of claim 24, wherein the MCC field ispopulated with a value indicating the UMA call request is made over theaccess network.
 26. The computer-implemented method of claim 24, whereinthe LAC and Cell ID fields are populated with a value pair thatidentifies the UMA call request as being for one of: an in-country call,an out-of-country call, a call made near a tower belonging to the UMAnetwork, and a call made near a tower belonging to another cellularnetwork.
 27. An Unlicensed Mobile Access Network Controller (UNC) havingcomputer-readable instructions for facilitating Call Detail Record (CDR)billing in an Unlicensed Mobile Access (UMA) network, the instructionscomprising: receiving a registration request associated with a UMAcapable handset over an access network, wherein the registration requestincludes identification information comprising at least one of: an IMSIID, a CGI_(REAL) ID, an SSID, and a MAC address; accessing a UMAdatabase with the identification information; receiving a CGI_(BILLING)ID from the UMA database; overloading at least one existing CGI fieldwith the CGI_(BILLING) ID such that the overloaded CGI field correspondsto a UMA call; identifying a call request from the UMA capable handsetover the access network; and communicating the overloaded CGI field to aMobile Switching Center (MSC) for the identified call request.
 28. TheUNC of claim 27, wherein the instructions further include: receiving apublic IP address associated with the access network from a SecurityGateway prior to receiving the request for registration; andcommunicating successful registration to the UMA capable handset. 29.The UNC of claim 27, wherein the CGI_(BILLING) ID includes at least oneof: a modified Mobile Country Code (MCC) field, a modified MobileNetwork Code (MNC) field, a Location Area Code (LAC) field, and a CellID field.
 30. The UNC of claim 29, wherein the MCC field is populatedwith a value indicating the UMA call is made via the access network, andthe LAC and Cell ID fields are populated with a value pair thatidentifies the UMA call as being one of: an in-country call, anout-of-country call, a call made near a tower belonging to the UMAnetwork, and a call made near a tower belonging to another cellularnetwork.
 31. A system for facilitating Call Detail Record (CDR) billingin an Unlicensed Mobile Access (UMA) network, the system comprising: aUNC that is configured to: receive a registration request from a UMAcapable handset using an access network, wherein the request includesidentification information comprising at least one of: an IMSI ID, aCGI_(REAL) ID, an SSID, and a MAC address; access a UMA database withthe identification information; receive a CGI_(BILLING) ID from the UMAdatabase; overload at least one existing CGI field with theCGI_(BILLING) ID such that the overloaded CGI field corresponds to a UMAcall; and identify a call request from the UMA capable handset over theaccess network; and an MSC that is configured to: receive the overloadedCGI field from the UNC for the identified call request; facilitate a UMAcall from the UMA capable handset in response to the call request; andcommunicate the CGI_(BILLING) ID to a billing system upon completion ofthe UMA call.
 32. The system of claim 31, wherein the UMA database isconfigured to determine the CGI_(BILLING) ID based on the receivedidentification information, wherein the UMA database includes at leastone of: a subscriber database, a service type database, a zonesdatabase, and an access points database.
 33. The system of claim 31,further comprising a Security Gateway that is configured to:authenticate the UMA capable handset by a Security Gateway prior toregistration; communicate a public IP address associated with the accessnetwork to the UNC as part of the authentication; and assign the UNCbased on the public IP address.
 34. The system of claim 31, wherein theUNC is further configured to overload the existing CGI fields such thatan MCC field is populated with a value indicating the UMA call is madevia the access network; an MNC field is populated with a valuecorresponding to a rating plan; and LAC and Cell ID fields are populatedwith a value pair that identifies the UMA call as being one of: anout-ofcountry call, a call made near a tower belonging to the UMAnetwork, and a call made near a tower belonging to another cellularnetwork.
 35. The system of claim 31, wherein the MSC is furtherconfigured to communicate a start time and an end time associated withthe UMA call to the billing system upon completion of the UMA call. 36.The system of claim 31, further comprising a CGI database configured tostore information associated with the UMA capable handset when it uses acellular network component of the UMA network.